pkg_in_pipe: move the plane cards of the builds of a tag to a given state - #840
pkg_in_pipe: move the plane cards of the builds of a tag to a given state#840glehmann wants to merge 1 commit into
Conversation
…tate Add move_cards_to_state.py, which keeps the plane cards of the XCPNG project in sync with the progress of the builds: the cards linked to the builds of a given koji tag are moved to a given state, and never backwards. Signed-off-by: Gaëtan Lehmann <gaetan.lehmann@vates.tech>
gduperrey
left a comment
There was a problem hiding this comment.
It bothers me a bit that the cards are being moved via a script based on the build location.
I’m worried we might start moving them just to keep things in sync, without verifying them first, which could result in them being incomplete.
|
I think a motivation is missing to this PR, as well as a description of the process update. It's already possible to bulk-move cards via the UI, and as others pointed out, moving states is supposed to come with checking that the conditions are met. The question is whether updating the cards status is a formality that needs to be automated, or the occasion for the release team to check that everything is in order. In particular, I'm against moving to "released" automatically without seeing any description of the new process, because that's currently when we check one last time that no documentation update is missing (though, at this stage, is rather late), and that we contact users in tickets, forum or github to let them know about a specific fix or feature they were waiting for. So, to consider this automation, we need to understand what the release process looks like with this tool. |
Add move_cards_to_state.py, which keeps the plane cards of the XCPNG
project in sync with the progress of the builds: the cards linked to
the builds of a given koji tag are moved to a given state, and never
backwards.
Signed-off-by: Gaëtan Lehmann gaetan.lehmann@vates.tech
This PR is part of a tree containing 4 PRs:
mastermaster